Attach LastResponse after unmarshaling #1123
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a resource has a custom
UnmarshalJSON
file likeCharge
does, we lose theLastResponse
property of theAPIResource
due to ordering.Additionally—there's a guard here which doesn't make much sense which I've removed. If
v
is ever nil here, we'd panic before hitting the guard.I found it kind of awkward to write a test for this behavior—the existing test in
stripe_test.go
doesn't expose it because it has no custom UnmarshalJSON defined; if you look at the definition forCharge
you can see it completely overwrites the object (as do several others).r? @brandur-stripe
cc @stripe/api-libraries